Buddy system for navigation devices

ABSTRACT

A buddy system for navigation systems is disclosed. Further to the buddy system, a user of a navigation device can locate other navigation device users within a select vicinity. The buddy system further includes buddy lists compiled from a number of navigation devices grouped according to a common characteristic. The characteristic may be a relationship among the users of the navigation devices, the location of the navigations, and the like. The navigation systems are listed within buddy lists according to identification and geographical location. The navigation systems, with buddy lists stored therein, may be made to navigate towards a select buddy. In addition, further to the buddy system, one navigation system can communicate with another via text and voice messages.

PRIORITY STATEMENT

The present application hereby claims priority under 35 U.S.C. §119 oneach of Great Britain Patent Application numbers 0604709.6 filed Mar. 8,2006; 0604708.8 filed Mar. 8, 2006; 0604710.4 filed Mar. 8, 2006;0604704.7 filed Mar. 8, 2006; and 0604706.2 filed Mar. 8, 2006, theentire contents of each of which is hereby incorporated herein byreference.

FIELD

The present application generally relates to the field of navigationsystems and more particularly to a buddy system for navigation systems,an arrangement for operating the buddy system with navigations systems,and a navigation system configured to affect operation of the buddysystem.

BACKGROUND

Navigation systems as used herein refer to devices enabling a user tonavigate from a current location to a destination location. Thenavigation systems may be arranged to provide user output in the form ofa displayed map upon which arrows or other indicia indicate anappropriate route between the current and destination locations. Themaps may be refreshed based upon, for example, current location asdetermined by appropriate satellite, GPS, and/or Internet connection.With refreshed maps come refreshed visual indicia as to an appropriatenext step along the route between current and destination location.Alternatively, map refreshing may occur with time. Other user output mayinclude voice direction made along with or independent of the mapdisplay. A common voice command may be to make a particular turn at anupcoming intersection.

The navigation systems may comprise an internal processor incommunication with an internal memory, communication means, power meansand a display. The processor may comprise software or other programmingto effect the generation of the above noted maps and user output. Theinternal memory may include map data upon which the process may drawupon. Additionally, the processor may be arranged to communicate with aremote server via the communication means. The server may be a dedicatedor non-dedicated server with the communication means being standarddirect and/or wireless communication.

The navigation system may be further arranged to receive user input viaa touch screen, buttons, voice activation and the like. The processormay be further programmed to receive the user input, determine a currentlocation via GPS and the like and display the current location on a mapobtained from memory. Further, once armed with a destination location,the processor may be programmed to determine a select and/or best routebetween the current and destination location and further output such asbest route via a series of output voice commands in conjunction withrefreshed map displays.

Current navigation systems come in a variety of forms. A form, personalnavigation device, may be handheld or otherwise portable and/or embeddedinto a motor vehicle such as a car, boat or plane. Among the navigationsystems many features is the ability to route the user to a particulardestination location or point of interest (such as a next gas station,favorite restaurant and the like). Such destinations are geographicallystatic and typically known in advance. For example, a user maypreprogram his or her device to identify a favorite bar in advance ofbeginning a trip to the bar. Upon embarking towards the bar, the userneed simply enter the bar's name or location.

A common functionality missing from navigation systems is the capabilityof routing a user towards a moving destination location. Additionally,another missing functionality is the ability to locate other navigationsystem users. Such functionality is especially helpful in answering suchimportant questions as “where is my wife?”, “where are my colleagues?”or “where are my friends?”. Such questions become even more importantnot only in a personal context of meeting friends or family but also ina professional context of a central office attempting to locatecolleagues currently underway—such as delivery vehicles, taxis and thelike.

SUMMARY

The present invention is therefore directed to the aforementionedunaddressed need in the art, namely the provision of locating,navigating towards and/or communicating with other navigation systemsusers. The present system for such provision is herein referred to as abuddy system. The present invention is accordingly directed to the buddysystem, a system for providing the buddy system and navigation systemsprogrammed or otherwise arranged to affect the buddy system.

The buddy system, per se, is a system by which one navigation system canlocate a select other navigation system or systems. The instant buddysystem provides users with functionality to select users of navigationsystems according to a predetermined commonality of the select users.For example, the buddy system enables one user to locate othernavigation system users or buddies in a particular location, i.e. allbuddies located in or around point x. The location of the buddies withrespect to point x may be varied. Additionally, the buddy systemprovides for the locating of select buddies belonging to a particularprofessional organization, i.e. select (or all) taxis in a greater cityarea or select (or all) delivery trucks currently in operationregardless of location, etc. The location of buddies may also be limitedto friends, family and the like, i.e. location of one's children. Buddygroupings may of course overlap and include more than one of theaforementioned. These and other groupings of buddies are detailed below.

To affect the aforementioned groupings, a predetermined list of buddies,or buddy list, is created. Once affected, the identification andlocation of buddies on the buddy list may be made. As the buddies arealso users of navigation systems, the buddy list may further include thegeographical location of the navigation system and therefore buddy usingthe located navigation system. As navigation systems tend to be used byusers in motion, the buddy list may be refreshed or updated periodicallyto remain current.

Once located, the requesting user may wish to navigate towards one ormore buddies on the buddy list as well as communicate with one or moreof them. The communication may take the form of voice or textcommunication. The buddy system is therefore further directed toeffecting such and related functionality.

The inventive system for affecting the buddy system comprises adedicated server in communication with one or more navigation systems.The system may follow the known client-server architecture with theadditional features and functionality to affect the instant buddysystem. In addition or alternative to a dedicated server, otherappropriately configured client-server systems, i.e. dedicated and/ornon-dedicated servers, may be employed. Navigation system to navigationsystem communication may be affected via a peer to peer configuration orvia the dedicated and/or non-dedicated server.

The present invention is further directed to a navigation system foraffecting the buddy system. The instant navigation system may comprise aprocessor programmed to affect the above noted functionality.Additionally, the instant navigation system includes input/output meansfor exchanging information with a user. Such input/output means mayinclude a touch screen, speaker/microphone, buttons, lights and the likewith the appropriate supporting functionality within the navigationsystem itself and/or remotely located on at least one of theaforementioned dedicated and non-dedicated servers, remote computers,remote navigation systems and the like. By way of an appropriatelyprogrammed processor, the user may be prompted with a series ofgraphical interfaces to manually input desired functionality. Theinputting may be manual, voice activated and the like. The desiredfunctionality may include the aforementioned buddy location, buddy listcreation, navigation towards a buddy, communication with a buddy and thelike.

The present system is still further directed to a method forimplementing the aforementioned buddy system.

While described above in the form of navigation systems, application ofthe present buddy system is not so limited to navigation systems and mayinclude implementation on portable or desktop computers, personaldigital assistants, mobile telephones and any other device including atleast the above mentioned elements and functionality.

BRIEF DESCRIPTION OF THE DRAWINGS

The present application will be described in more detail below by usingexample embodiments, which will be explained with the aid of thedrawings, in which:

FIG. 1 depicts the instant buddy system by way of a first navigationsystem querying for the location of another navigation system;

FIG. 2 is a flowchart depicting a method for affecting the present buddysystem on a navigation system;

FIGS. 3-12 depict a series of screen shots which may be presented to auser affecting the present buddy system on a navigation system.

DETAILED DESCRIPTION OF THE EXAMPLE EMBODIMENTS

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the presentinvention. As used herein, the singular forms “a”, “an”, and “the” areintended to include the plural forms as well, unless the context clearlyindicates otherwise. It will be further understood that the terms“includes” and/or “including”, when used in this specification, specifythe presence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

In describing example embodiments illustrated in the drawings, specificterminology is employed for the sake of clarity. However, the disclosureof this patent specification is not intended to be limited to thespecific terminology so selected and it is to be understood that eachspecific element includes all technical equivalents that operate in asimilar manner.

Referencing the drawings, wherein like reference numerals designateidentical or corresponding parts throughout the several views, exampleembodiments of the present patent application are hereafter described.Like numbers refer to like elements throughout. As used herein, the term“and/or” includes any and all combinations of one or more of theassociated listed items.

The present invention will be discussed with respect to a portablenavigation device (PND) with the understanding that the presentinvention may be applied to any navigation system or other deviceincluding the functionality discussed herein.

FIG. 1 depicts a typical client server arrangement 15 comprising aserver 10 in communication with a generic user 14 and a tablet computer12 and a personal navigation device (PND) 16. Each of the aforementionedincludes communication means, known in the art and not depicted infigure, arranged to facilitate communication 18 with the server 10. Inaddition, each may comprise input/output means for exchanginginformation with a user. Such input/output means may include a touchscreen 17 upon which a map 19 is displayed and user commands tacticallyinputted as is depicted on the personal navigation device 16. The touchscreen may further be used to display graphical user interfaces(detailed below) prompting the user commands. Other input/output meansinclude speaker/microphone arrangements for receiving and broadcastingvoice commands; buttons for receiving tactile prompts and/or displayinga prompt through flashing or the like; and other input/output means asmay be envisioned by one skilled in the art. The present invention isnot limited to the number or type of client interacting with the serverand the aforementioned generic user, tablet computer and personalnavigation device are depicted by way of non-limiting example.

The server comprises a buddy list 11 made up of a plurality of buddies13. As will be detailed below, the buddies may be selectively organizedand identified by either or both identification and geographicallocation. The server may be a dedicated or non-dedicated server. Theserver may be a stand alone server or part of a larger network.Communication with the server may be affected by means known to oneskilled in the art. The present invention is not limited by clientserver architecture nor client or server type.

Because the buddy list may be populated by buddies within a certainradius of the requestor, the server may maintain a master list ofavailable buddies and their current locations. Accordingly, as will bedetailed below, a user when signing on to the buddy system may berequested to allow the release of his or her current position.Additionally, the server further includes processing means available tocalculate a current requester position, apply a certain geographicalradius to the current position and select from among the possiblebuddies for, among other criteria, buddies within the radius.

FIGS. 2 a-c depict flowcharts depicting a method for affecting thepresent buddy system on a navigation system. The depicted methodhighlights the interaction between device and user, including theaffects of user selection of a particular functionality. The presentinvention is not limited to the specific depicted order. The method willbe discussed with respect to application on a personal navigation device(PND) with the understanding that the present method may apply to anyclient. The method steps will be discussed below with screen shotsdepicting icons for affecting the discussed method steps.

A top menu may comprise the map 19 depicted in FIG. 1. Tapping on themap or otherwise engaging the PND will cause a main menu to appear. Thepresent buddy system may be part of a typical functionality provided bynavigation software, the functionality appearing as one of many mainmenu icons. Alternatively, the buddy system may be an add-on systemprovided in addition to a main functionality. Such is offered by theassignee TOMTOM entitled PLUS.

When part of the PND, the Buddy System first becomes noticeable via amain menu icon such as is depicted in FIG. 3. FIG. 3 depicts a highestlevel icon 300 introducing the buddy functionality to the user. Thefunctionality may be part of a navigation software package for anavigation system or an add-on to existing packages by way of anenhancement. Activation of icon 300 causes buddy system menus to appear.The activation also corresponds to the start 20 of the flowchart ofFIGS. 2 a-2 c.

In a first step 22, prior to the display of buddy system menu orconcurrently therewith, a buddy list request is sent by the PND to theserver.

The buddy list comprises a grouping of navigation device users, thegrouping being based upon a preexisting relationship set up by the user.The buddy list comprises user names and/or current geographicallocations of the users. A depiction of a buddy list is set out below.Buddy lists are maintained by a central server and periodicallyrefreshed. As will be detailed below, the user may selectively refreshthe downloaded buddy list saved on his or her PND. The differentcategories or groupings of the buddies, as suggested above, may be basedupon a relationship to the user (e.g. family, profession, etc.) orrandom (e.g. any other buddy systems users). The buddy list may furtherbe limited by geographical location, such as a select radius to acurrent or select location.

In step 24, the server communicates the requested buddy list to the PND.

In step 26, the PND creates a local shadow/working list of the buddylist.

In step 28, the server registers the client's request. The above stepsmay occur automatically without the direct knowledge of the user.

The following queries are depicted as icons in a first of two buddysystem menus. The specific pictorial depiction and corresponding textmay vary by application and are depicted in the Figures as example iconsonly. The first buddy system menu 400 is depicted in FIG. 4, the menucomprising a number of icons corresponding to queries discussed inconjunction with the flowchart below.

Returning to FIG. 2 a, in step 30, the user is queried whether toinclude his or her name and geographical location in other buddy listsstored on the server or whether the user wishes to remain anonymous.Icon 440 of FIG. 4 corresponds to this query. Should the user wish toremain anonymous (32), he or she will appear to other users as havingturned his or her device off. The icon 440 may further be caused tochange thereby indicating that the user is hiding his or her identityand location. Such an icon may include a cross through the icon asdepicted in FIG. 4. The user unavailability is affected by sending aSet-Status/unavailable message to the server from the user PND. Theresult returned by server is processed appropriately.

If the user decides to have his or her name included in the list (34),the appropriate buddy list or lists stored on the server will be updatedwith the user's information in step 36. This will be affected by sendinga Set-Status/available message to the server from the user PND. Theresult returned by server is processed as will be detailed below.Thereafter, the first Buddy System menu 400, FIG. 4 will be displayed tothe user.

In addition to the aforementioned, the user may be asked if he or shewishes to adopt a special name which will be used in place of genericdevice identification. If so selected, the server will store the user'spersonally selected name. Further, if the buddy list requested from theserver is empty, the hide your positions icon (below) will be dimmed.

Pursuant to the first Buddy System menu, the user is presented withadditional options, including: guided tour 38 (icon 432), showing abuddy's location on a map 40 (icon 434), update (the buddy list) now 42(icon 436), inviting a new buddy to the buddy list 44 (icon 438),proceeding to the second menu 46 (icon 438) and done 48 (icon 440).First Buddy System Menu 400 may include further displayed information,including current time 442, indication of when a last update wasperformed 444 and an indication of which of the two Buddy System menusis being displayed 446.

Returning to FIG. 2 a, if the guided tour option 38 is selected 50, thePND user is provided with a guided tour of the buddy system 52. Theguided tour may comprise a multimedia tour including visual and verbalfeedback to the user. The tour may further be instructional andinteractive. Software used for implementing and affecting the guidedtour may be stored locally on the navigation system or remotely on theserver or the like and downloaded when engaged by the user. The detailsof the tour are a matter of design.

Queries and/or options may be engaged or selected via example pressingthe icon on the PND display, the display being touch sensitive. Otheruser input means include voice activation, buttons and the like.

Returning to FIG. 2 a, if the show buddy option 40 is selected 54, a mapview (500, FIG. 5) is displayed on the PND's display 55, the mapdepicting a location of a particular buddy in question indicated thereonwith the exact current location (as known by the server) highlightedwith indicia. An additional step may be the notification of thedisplayed buddy that his or her location was requested by the user. Byway of example, a map is depicted on the PND of FIG. 1.

FIG. 5 depicts an example map view 500 of Amsterdam, with a particularbuddy in question 502 depicted thereon 504. The map view includes otherfunctionality including: Find 504, Options 506 and Done 508; which willbe discussed in more detail below.

Returning to FIG. 2 a, the update now option 42 (icon 436, FIG. 4)actually comprises two options: an Update Now option and an Update orUpdate Buddy option. Alternatively, the Update Buddy option may bepresented by way of individual query or icon (as is the case with step74). When the update now option 42 or update buddy option 74 is selected56 and 58 respectively, the server is requested by way of a refreshmessage to update the identities and locations of persons on thereceived buddy list 60 and 62 respectively. Process 62 will be discussedin more detail below. The result returned by server is processed and theuser is presented with the first menu screen or buddy list on the user'sPND display. Pursuant to the Update Now option 42, the current state andlast known geographical positions (when available) of all the buddies onthe buddy list are retrieved by the server.

FIG. 6 depicts a typical buddy list 600. As depicted, the buddy listcomprises a plurality of buddies 602 identified by e-mail address 604and buddy icon 606. Further to the present invention, each buddy may beidentified by a particular icon having particular significance.Different buddy icons are depicted in FIG. 7. The buddy list 600 furtherincludes an indication of time 608, a title 610 and three options: find612, update 614 and cancel 616. Pursuant to the find option 612, theuser is presented with an interface to locate a particular buddy fromthe buddy list via a search function, the search function being known inthe art. The update function 614, once activated, updates the buddy listwith the most current information available on the buddies, theinformation originating either from the user's PND or the server. Thecancel function 616 closes the buddy list and returns the user to eitherthe first buddy system menu or to the PND's main menu.

FIGS. 7 a-7 e depict one buddy icon each. The icons may be color codedfor easier identification. First buddy icon 702 is used to indicate thatthe respective buddy is available and his/her position is current. Bycurrent, it is meant that the position is no more than 15 minutes old.Alternatively, other time definitions of current may be applied. As thisbuddy is current and available, his/her position can be seen on the map(e.g. 502, FIG. 5).

Second buddy icon 704 is used to indicate that the respective buddy isavailable although his/her position is out of date. In other words, thisbuddy's position was known but has since gone stale. A stale positionmay be one that is between 15 and 60 minutes old. Alternatively, othertime definitions may be applied. This buddy could still be depicted onthe map.

Third buddy icon 706 is used to indicate that the buddy is availablealthough his/her position is old, namely more than 60 minutes. Here too,the time may vary by application. This buddy could still be depicted onthe map.

Fourth buddy icon 708 is used to indicate that the buddy is unavailableand the server is waiting for a reply to an invitation to the buddy tojoin the buddy list. This buddy has not yet responded to an invitationto become buddies. Accordingly, this buddy or potential buddy is onlyvisible on the buddy list.

The fifth buddy icon 710 is used to indicate that the buddy isunavailable and the buddy's position cannot be determined because thebuddy has declined the invitation to become buddies. Additionally, thebuddy may have deleted the user from his/her buddy list.

Information may be retrieved by the server from a database, themaintenance of which may be made by the server further to proceduresknown in the art. Further to the Update Buddy option 74, the server iscaused to actively request one particular buddy to return his or hercurrent geographical location via a push channel or the like. Thefollowing interactions occur based upon the state of the buddy at issue.The updating can also occur from the buddy list screen option 614.

If a buddy state is unavailable/unknown, then a message may be displayedto the user along the lines of: TOMTOM BUDDIES, <Name> is not a PLUSuser—PLUS being an enhanced service available for navigation systemsfrom the assignee of the present application TOMTOM, the serviceincluding the present buddy system. Other language may be used to theeffect that the requested buddy is not a member of the buddy system.

If the buddy state is unavailable/deleted (i.e. the buddy has beendeleted user from the list of buddies), then a message may be displayedto the user along the lines of: “TOMTOM BUDDIES, <Name> has deleted youfrom his/her list of buddies.”

If the buddy state was unavailable/invited and is now available (i.e.the buddy has accepted the user's invitation to become buddies), then amessage is displayed to the user along the lines of: TOMTOM BUDDIES,<Name> has agreed to be your buddy.

If the buddy state was unavailable/invited and is nowunavailable/declined (i.e. the buddy has declined user's invitation tobecome buddies), then message is displayed to the user along the linesof: TOMTOM BUDDIES, <Name> has declined to be your buddy.

If the buddy state is invited/reply-to-invitation (i.e. the buddy hasinvited user to become buddies), then the user is presented with thefollowing text message: TOMTOM BUDDIES, <Name> has invited you to becomebuddies. The user is further presented with a pair of buttons foraccepting or declining the invitation. If the user selects Accept, aReply-to-Invitation/accepted message is sent to server. If the userdeclines, a Reply-to-Invitation/declined message is sent to server.

At the server, in response to the Reply-to-Invitation/accepted message:the state of accepting a buddy in list of buddies of inviting buddy ischanged to available from unavailable/invited; the state of invitingbuddy into list of buddies of accepting buddy is changed to available(was invited/reply/-to-invitation); responsiveReply-to-Invitation/declined message—the state of declining buddy inlist of buddies of inviting buddy is changed to unavailable/declined;the inviting user is deleted from the list of buddies of decliningbuddy; and the local list of buddies is updated.

Updating the buddy list can be done automatically on a time delay set bythe user. This can be set manually by the user when engaging the changebuddy preferences 64. If engaged 66, the user is presented with anupdate screen 800 depicted in FIG. 8. Pursuant to FIG. 8, the user ispresented with text 802 indicating an automatic buddy list update modeand a check box 801 checked when the automatic update mode is engaged.In addition, the update screen 800 includes a time indication 804 andtitle 806. The user is further presented with an option to end thefunction (Done, 808) which brings the user back to the first buddysystem menu. If the check box 801 is unchecked, a second update screenis displayed to the user, the second screen including a numeric editor900, FIG. 9, which facilitates user entry of a select time delay betweenupdates in minutes 907. The editor 900 further includes a back function902, a cancel function 904 returning the user to the first buddy systemmenu and a done function 906 bringing the user back to the first updatescreen. As with the first update screen, the second update screenincludes a time indication 908 and title 910.

Returning to FIG. 2 a, if the invite new buddy option 44 is selected 58,the user identifies a particular buddy and requests the server to addthe identified buddy to a user specified buddy list 62. To affect theidentification of a new buddy for the buddy list, the user is presentedwith a standard alphabet editor screen 1000, FIG. 10 includingalphanumeric characters as well as options to cancel 1010 and done 1012.New buddies may be identified by e-mail address 1014 or otheridentifier. To effect the addition, an invite message is sent to theserver by the user PND and the result returned by server is processed.Hereafter, the buddies or first menu is again displayed. As with theabove screens, the alphabet editor screen includes a clock 1016 and tide1018.

At the server side, a determination is made whether the user exists andis otherwise available or known. If the status of the user is available,the user is added to the buddy list by way of aninvited/reply-to-invitation step. The intended buddy is informed of theinvitation by means of a message notification which can be personalizedby the user or comprise prewritten text available from a memory and sentautomatically as part of this step. If the buddy is unknown, then thebuddy state becomes unavailable/unknown and the user is so informed. Ifthe user is not available, the buddy state becomes unavailable/invitedand the user so informed. If the buddy is available, the buddy statebecomes available.

The server may further contact the identified buddy and query him or herfor permission to add him or her (with or without current location) tothe user specified buddy list. Alternatively, the aforementioned may beperformed without identified buddy confirmation or input.

Returning to FIG. 2 a, if the user elects to exit the buddy system 66further to option 48, the user exits the buddy system 68 and is returnedto the map view or main menu of his/her PND.

If the proceed to the next menu 40 is elected 62, the first menu will bereplaced by a second menu presenting the option with additional optionsdiscussed below. As with the first menu, each of the second menu queriesmay be presented simultaneously on one screen. An alternative number ofqueries may be presented depending upon programming, screen size and thelike. The present invention is not limited by the number of graphicaluser interface queries presented on any one screen at any one time.

If further to option 46, the user elects to proceed to the next buddysystem menu 70, the user is then presented with the second buddy systemmenu 1100 as depicted in FIG. 11. FIG. 11 comprises a series of iconsrelated to method steps set out in FIG. 2 a.

Returning to FIG. 2 a, the user is presented with a series of queries oroptions (via the second buddy system menu 1100 icons), including: sendbuddy a message 78 (icon 1102); change buddy preferences 64 (icon 1110),delete buddy 72 (icon 1104), update buddy 74 (icon 1108) and readmessages 76 (icon 1106). The user is further provided with the option toproceed to go back to the previous menu 80 (icon 1112) and end 81 (icon1114).

If the send buddy a message option 78 is elected 82, a send buddymessage sub/menu screen 1200 is displayed for the user, the screen beingdepicted in FIG. 12 and the process continuing 84 in FIG. 2 b. The useris presented with several options or queries, including: send buddy amessage 88 (icon 1204); send buddy a location 90 ( icon 1202); sendbuddy your position 92 (icon 1206); and done 86 (icon 1208).

If the send buddy message 88 (icon 1204, FIG. 12) is elected 98, theuser's PND transmits a message to a select buddy 104. The message maycomprise text, voice, images, combinations of the aforementioned and thelike and may be transmitted via the server or peer to peer. The messagemay further be pre-stored messages stored within the server andavailable for transmitting by request of the user on the PND. Details ofexchanging messages in general are set out below.

If the send buddy a location option 90 is elected 96, a user selectedgeographical location is transmitted to the buddy in question 106 alongthe same lines as the above message. An example message 1300 is depictedin FIG. 13. The message comprises text identifying the selectedgeographical location 1302 and the GPS position 1304 for the location.The message further comprises two options, namely proceeding to anavigation to menu 1306 and returning to the main map or main menu ofthe PND 1308. The message may further include a time 1310 and title withindication of sender and telephone number thereof 1312.

The buddy must have an available state and accordingly a list of buddiesto whom such a message could be sent may be limited in advance, by thePND, to only those with that state. A send buddy location screen mayfurther be displayed to the user in conjunction with this option, thesend buddy location screen including a GPS icon facilitatingdetermination of a position. Selection of the GPS icon brings up alocation menu screen through which a location may be selected orotherwise inputted. One possible location is the user's currentposition. Once a location is selected and entered by the user, aSend-Position message is sent to the server. The message may includepredetermined explanatory text or personalized text. The result returnedby server is processed and the first menu is displayed for the user.

Upon receipt at the buddy's navigation device, the transmittedgeographical location may be displayed as a text and/or as a location ona map. The user selected geographical location or address may be createdby typing in alphanumeric characters off of a displayed alphabet;tactically indicating on a displayed map the location, or other inputmeans. Such may be provided via a location selector in a text message.The now entered location is transformed into a message and transmitted,via the server or directly to the buddy's navigation system.

If the user elects to send buddy current location 94 pursuant to step92, a request is sent from the PND to the server for the buddy's currentlocation 108. The sever then locates the record corresponding to thebuddy's current location (as may be available pursuant to a refreshedbuddy list or obtained automatically or by permission from the buddy)and transmits the location to the PND which in turn displays thelocation as either a text or indicia on a map. An example of a mapdepicting a buddy is set out in FIG. 5.

If the cancel option 86 is selected 100, the method proceeds 102 back tothe pervious menu. Alternatively, the method may proceed to end.

Returning to FIG. 2 a, if the change buddy preferences option 64 (icon1110, FIG. 11) is elected 110, a change buddy preferences screen(discussed above) is brought up and displayed on the user's PND display84. Pursuant to this screen, the user is provided with the option toselect an automatic update of the buddy list from the server, theupdating comprising the names of current buddies (i.e. buddies who havecurrently activated their navigation devices and have agreed to be partof the buddy list) as well as the current buddies current locations asagain obtained from the buddy navigation systems as discussed above.Pursuant to an additional automatic updated buddy list screen, the useris presented with the option to selectively update the buddy list everynumber of minutes, the number ranging from 1 to 99. To facilitate inputof the updating time interval, the user is presented with a series ofnumbers 1-9 along with the options to cancel, finish and go back to aprevious menu (as will be detailed below). Pursuant to the updating ofthe buddy list, the user's PND will be made to forward the user'scurrent identification and geographical location to the server forinclusion in appropriate buddy list(s).

If the delete buddies option 72 (icon 1104) is selected 114, the user ispresented with text requesting a confirmation of the deletion. The textmay read, “Are you sure you want to delete <Name>?” Other text may beused by way of design choice. The user is further presented with a yesand no selection option. Such option may be a button, icon, voiceactivation means and the like. If the user selects “yes”, the buddy isdeleted from the local list of buddies (on the user PND or storedremotely), a Delete-Buddy message is sent to the server and the resultreturned by server is processed. At the server, the buddy to be deletedis removed from the user's buddy list, the state of the deleted buddy isset to unavailable/deleted and the buddy list is displayed for the useron his or her PND display. Likewise, the user is deleted from buddylists belonging to the now deleted buddy.

If the update buddy position option 74 (icon 1108) is selected 58, adetermination is made of all buddies having an available state and aGet-Position message is sent by the user's PND to the server—theposition being that of the available buddies 62. The result returned bythe server is processed and the first or buddy menu is displayed to theuser. At the server, if the statue of the intended buddy whose positionis being updated is available, a Give-Position message is sent to theintended buddy (e.g. via Push) and the buddy returns his/her currentposition. The position of the buddy on the server is further updated.

If the user elects to read messages 118 pursuant to the read messagesoption 76 (icon 1106), the user is presented with a text message 120.The text message 120 may comprise the user's position and identificationas will be detailed below with respect to FIG. 13. Pursuant to thedisplayed message in step 120, the user is presented with additionaloptions step 122 set out in by way of the flowchart of FIG. 2 c.

As depicted in FIG. 13, message 1300 comprises a location 1302 and buddyidentification 1304 presented here as text. Other message formats may beused as envisioned by one skilled in the art, including pictures, soundsand other media. The message 1300 further includes an indication of thesender 1310 displayed therein. The sender may be identified by name andtelephone number. As depicted, message 1300 was sent by Johnny havingtelephone number +31653354300 (1310). The current time (1312) may alsobe displayed. The precise presentation of the sender information andtime is matter of design choice. Alternatively, other relatedinformation may be displayed within the message, including: currentdate, personalized sender identification and the like.

Pursuant to the message 1300, the user is presented with the option toexit the message (done) 1306 which if selected exits the buddy systemfunctionality and returns to a main map display or other high leveldisplay. Pursuant to the message 1300, the user is presented withoptions 1308 which if activated brings up a navigation screen menu 1400depicted in FIG. 14 with correspondence to the flowchart of FIG. 2 c.

Returning to FIG. 2 c, the user is presented with a number of options,namely: navigate there 126 (icon 1402, FIG. 14), show on a map 128 (icon1404, FIG. 14), add as favorite 130 (icon 1406, FIG. 14) and cancel 124(icon 1410, FIG. 14). The aforementioned options operate in conjunctionwith possession of a buddy address.

If the user elects to cancel 138 further to the cancel option 124, themethod reverts back 140 to the second buddy system menu, a screen shotof which is depicted in FIG. 12.

If the navigate there option 126 (icon 1402, FIG. 14) is selected 136,the user's PND will affect a navigation to the particular geographicallocation 132. Initially, the user will be queried about a specificarrival time step 148 (1500, FIG. 15). If a specific arrival time (1502,FIG. 15) is selected by the user 166, a route is calculated to the buddylocation by the PND software which will affect arrival at the userdesired time. Likewise, a best route will be calculated if no specificarrival time 168 (1504) is selected by the user 156. The affect may bemade by determination of a best route from the user current location tothe particular geographical location as may be effected by appropriatenavigation software such as the NAVCORE software from this patent'sassignee TOMTOM. The best route may be displayed on the user's PND aswell as be accompanied by voice commands and the like.

If the user elects to have a buddy location displayed on a map 134pursuant to query 128, the PND is made to decipher the buddy location asmay have been received pursuant to an earlier query and display the same(step 144) on a map as depicted in FIG. 5. Prior to display, the stateof the buddy for display is confirmed as being available. If availablethe buddy information is taken from the local list and displayed on thePND. The display may include a particular icon for emphasis 502, FIG. 5.The user is presented with the option of returning to the main mapdisplay or main menu by selecting icon 508. A route may be calculatedfrom the user's current location to the buddy by activation of the findicon 504. Likewise, the aforementioned navigation menu options step 122,FIG. 2 c may be accessed through activation of icon 506.

If the user elects to add a buddy location to his favorites 132 pursuantto option 130, the PND is made to store into memory the particularlocation 146 via entry of the buddy identification pursuant to analphanumeric editor screen as is depicted in FIG. 10 and discussedabove. If the entry already exists within the favorites list, the userwill be given the option of replacing the existing entry as depicted byscreen shot 1600 in FIG. 16 (query 150, FIG. 2 c). Such messages may beflash messages. Screen shot 1600 includes a yes 1602 and no 1604 option.In the event the user elects to make the replacement (154, FIG. 2 c),the prior entry of the same location is replaced with the new location(156, FIG. 2 c) within the favorites list. If the user elects not tomake the replacement (158, FIG. 2 c), the step ends and screen 1700 ispresented to the user (152, FIG. 2 c) giving him/her the option to setthe current location as a home location. Screen 1700 includes a yes 1702and no 1704 option. If the yes option 1702 is selected (160, FIG. 2 c),the PND is made to change the current home location to the one depictedon screen 1700 (162, FIG. 2 c). If the user elects not to replace thecurrent home location (164, FIG. 2 c), the user is brought back to thenavigation screen 1200 (140, FIG. 2 c) as depicted in FIG. 12.

In the event the cancel option 118 (icon 1214, FIG. 12) is elected 138,a previous menu is depicted 116 or the method ends.

Returning to FIG. 2 a, should the user elect to proceed to a previousmenu 83 (1112, FIG. 11) pursuant to option 80, the method reverts back(step 102) to the first buddy system menu as depicted in FIG. 4. Shouldthe user elect to finish 85 (1114, FIG. 11) pursuant to option 81, themethod ends (step 160).

Message exchanges with the server, in general, will now be discussed anddata managed by the server will also be outlined.

All Messages Sent by Client to Server Contain the Following Elements:

-   own status: available or unavailable-   own current position if status is available; otherwise empty    All Server Responses to Messages Sent by Client Contain these    Elements:-   list of buddy items

There are 2 paths of communication between buddies. One is the buddyclient-server message protocol, the other is text messaging. The buddyclient-server message protocol covers requests such as AddBuddy,RemoveBuddy, Update. A response received from the server is the resultof a manual user action: selecting a menu icon. A server response maycause a notification dialog to be shown on the client. Text messagingcovers ordinary text, which may contain a position recognized by theapplication. These text messages could be read as normal text ifreceived on a device that does not interpret them correctly. Themessages could be typed in manually. It does not matter if theyoriginate as an SMS, a server message, or a buddy message. The referredto visual notification is the indication that a text message has arrived(AFAIK this is general messaging functionality).The server sends acanned text message when a user is invited to become a buddy (i.e. whenit receives an AddBuddy request).

1. A server comprising means for communicating a buddy list to at leastone navigation device.
 2. The server according to claim 1, wherein saidbuddy list comprises a name and location of at least one navigationdevice.
 3. The server according to claim 2, wherein said buddy listcomprises at least one navigation device having at least one selectcharacteristic.
 4. The server according to claim 3, further comprisesmeans for at least one of grouping, updating and storing records relatedto said characteristic.
 5. The server according to claim 4, wherein saidcharacteristic comprises at least one of: a location, an interest, anactivity, an employment and an interpersonal relationship.
 6. The serveraccording to claim 1, further comprising means for receiving a requestfrom at least one navigation device and communicating said buddy list inresponse to said request.
 7. The server according to claim 4, furthercomprising means for querying said at least one navigation device forcurrent location information and identification.
 8. The server accordingto claim 7, wherein said means for updating further comprises means forupdating said buddy list in accordance with said current locationinformation.
 9. The server according to claim 1, further comprisingcommunication means arranged to affect communication between at leasttwo navigation devices.
 10. A navigation system buddy system,comprising: at least one buddy list comprising a number of navigationdevices grouped according to a common characteristic, and means forcommunicating said at least one buddy to said navigation devices. 11.The navigation system buddy system according to claim 10, wherein saidnavigation devices are listed in said buddy list by name andgeographical location.
 12. The navigation system buddy system accordingto claim 11, wherein said geographical location is provided by saidnavigation devices.
 13. A navigation device comprising communicationmeans arranged to send and receive buddy system messages.
 14. Thenavigation device according to claim 11, wherein said messages arecommunicated between at least one of navigation devices and a server.15. The navigation device according to claim 11, wherein said messagescomprise a request to a server for transmitting a buddy list to saidnavigation device.
 16. The navigation device according to claim 13,wherein said buddy list comprises a number of navigation devicesidentified by name and geographical location.
 17. The navigation deviceaccording to claim 14, further comprising means for outputtingnavigation instructions from a current location to said geographicallocation.
 18. The navigation device according to claim 17, wherein saidinstructions comprise at least one of audio instructions and visualinstructions depicted on a map background.
 19. The navigation deviceaccording to claim 13, further comprising means for determining which ofsaid navigation devices listed on a select buddy list is located withina radius of a select geographical location.
 20. The navigation deviceaccording to claim 19, further comprising means for displaying saidnavigation devices listed on a select buddy list is located within aradius of a select geographical location; and means for editing saidbuddy list.